Release 10.1A: OpenEdge Development:
Progress Dynamics Advanced Development

Registering the new manager

Now that you have completed the manager procedure, you must make it available to the Session types that need it. Remember that you have both a client version and a server version. The server version, fldedsrvrp.p, must be specified for any session that expects to have the Repository database connected. This would include both server-side AppServer session types and stand-alone client-server session types. The client version of the procedure, fldedclntp.p, should be added to a client Session Type that will not have the database connected.

To register the new manager:

Register each version of the procedure in the Repository by opening it in the AppBuilder and selecting File Save To Repository.
Select the Product Module the procedure should be associated with and the Object Type Procedure, as shown:



Select the Manager Type Control from the Administration Session menu, and select Add to create a record for the Field Edit Manager, as shown:



Give it a Manager Type Code of FieldEditManager. This is the logical name you can then use to invoke procedures inside the manager, as you saw earlier in the dynlaunch.i call. Enter a more descriptive Manager Type Name, which will appear in messages and in the drop-down list of managers displayed elsewhere, and select No static handle from the list of possible Static Handle values.
Check the System Owned toggle box on if you want access to this definition to be restricted. Check the Write to Config toggle box on to have this information written out to the configuration file. You must do this if you want to put the new manager in the Required Managers list for any Session Type, and have it prestarted for you as part of the session.
Save this Manager Type information, and return to the Manager Type Control, as shown:



Back in the Session menu, select Session Type Control, and select the Session Type(s) you want to add either the client or server manager to. Edit the Session Type, select the Manager tab, and select the Add button inside the folder to add the new manager. Note that the new manager appears in the drop-down list of manager types to choose from, as shown:



Specify either the client procedure or the server procedure as the Object Filename, whichever is appropriate, and pick the next available Startup Order for the manager, so that it is the last one started.

This example shows the list of Required Managers after adding the Field Edit Manager to the ICFDev Session Type, as shown:



Back in the Session Type Control window, select Option Generate Configuration File to regenerate the configuration XML file with the new information, as shown:



Now if you check the contents of that configuration file, you see the new manager listed for the sessions you added it to, as shown: